Blog

Brad Wood

March 27, 2014

Spread the word


Share your thoughts

REST APIs are a popular and easy way to add HTTP endpoints to your web applications to act as web services for third parties or even other internal systems. REST is simpler and requires less verbosity and overhead than other protocols such as SOAP or XML-RPC. Creating a fully-featured REST API is easy with the ColdBox Platform. Everything you need for creating routes, massaging data, and enforcing security comes out of the box.

The ColdBox MVC Platform has had excellent support for REST APIs for years and is a great choice for your next project.  Using ColdBox automatically affords you many productive features, including (but not limited to) the following:

  • Flexible and simple URL Routing
  • No XML configuration!
  • Easy use of conventions
  • Built-in data rendering
  • Easy control of HTTP verbs and status codes
  • Error Handling
  • Security
  • Caching

Have a read through our ColdBox REST documentation: Building ColdFusion Rest APIs

Also check out our companion project that helps you write and test REST APIs called ColdBox Relax: ReSTful Tools For Lazy Experts

 

Add Your Comment

(2)

Mar 28, 2014 16:44:10 UTC

by Henry Ho (@henrylearn2rock)

Question, can you how does ColdBox REST support compare to CF10's RESTFul API support? Would CB's be easier to test / reload vs CF10's implementation?

Mar 28, 2014 16:55:55 UTC

by Luis Majano

Henry, cf10's approach to rest is very rigid in my opinion. Ours is based on MVC best practices and the other one on just creating CFCs with all kind of annotations to expose the end points. YOu have to reload configurations with cf10 and there is not one place where you can see your routing or even alias routing. With ColdBox, we create a router file approach where you can define your URL mappings and use it not only for REST but for much more. It also allows for MVC to shine with your RESTFul application. Me personally, I would never leverage the built-in RESTful services as it is too messy in my opinion.

Recent Entries

12 Days of BoxLang - Day 4: TestBox

12 Days of BoxLang - Day 4: TestBox

Today we’re celebrating one of the most exciting new additions to the BoxLang ecosystem:

the TestBox BoxLang CLI Runner — a fast, native way to run your TestBox tests directly through the BoxLang Runtime. ⚡

No server required. No CommandBox needed. Just pure, ultra-fast BoxLang-powered testing from the command lineon Windows, Mac, and Linux.

If you’re building modern applications with BoxLang — web apps, CLIs, serverless functions, Android apps, or OS-level utilities — this new feature gives you a unified, flexible testing workflow you can run anywhere.

Victor Campos
Victor Campos
December 13, 2025
12 days of BoxLang - Day 3: SocketBox!

12 days of BoxLang - Day 3: SocketBox!

As BoxLang continues evolving into a modern, high-performance, JVM-based runtime, real-time communication becomes essential for the applications we all want to build: dashboards, collaboration tools, notifications, live feeds, multiplayer features, and more.

That’s where SocketBox steps in — the WebSocket upgrade listener built to work seamlessly with CommandBox and the BoxLang MiniServer. ⚡

Today, for Day 3, we’re highlighting how SocketBox supercharges BoxLang development by giving you fast, flexible, and framework-agnostic WebSocket capabilities.

Maria Jose Herrera
Maria Jose Herrera
December 12, 2025
12 Days of BoxLang - Day 2: CommandBox

12 Days of BoxLang - Day 2: CommandBox

BoxLang + CommandBox: The Enterprise Engine Behind Your Deployments

For Day 2 of our 12 Days of Christmas series, we’re diving into one of the most powerful parts of the BoxLang ecosystem: CommandBox the defacto enterprise servlet deployment platform for BoxLang.

If BoxLang is the language powering your applications, CommandBox is the engine room behind it all. ⚙️

Victor Campos
Victor Campos
December 11, 2025